View Issue Details

IDProjectCategoryView StatusLast Update
0000581T99X171.00 SKB EagleSW Issuepublic2019-04-17 09:11
Reporter(ALTech) Eric KimAssigned To(ALTech) Eric KimDue Date
PriorityhighSeveritys2-severeReproducibilityalways
Status closedResolutionfixed 
Summary0000581: [BT] STB keeps BT disconnection status when another type's RCU tries to connect BT
DescriptionIt has been occurred that the paired BT RCU keeps the disconnection status when another type's RCU tries to do BT pairing and its BT pairing is failed.

[Test Procedure]
1. Make sure that BMM-B01(Mobon) RCU is in BT connection
2. Try to do BT pairing by BRM-B01(RomoteSolution) RCU

[Actual Result]
The paired BMM-B01(Mobon) RCU is disconnected and it's been in BT pairing status when BRM-B01(RemoteSolution) RCU tries to do BT pairing and it's failed. and BMM-B01(Mobon) RCU is operated by IR mode.

[Expected Result]
The paired BMM-B01(Mobon) RCU must be in BT connection since another RCU)BRM-B01(RemoteSolution)) is failed on BT pairing.
TagsNo tags attached.
Attach Tags

Users monitoring this issue

Activities

(ALTech) Eric Kim

2019-03-25 16:45

developer  

(SW) Kerwin Chen

2019-03-25 18:05

developer   ~0001700

Hi Eric,

Could you update how to do BT pairing by BRM-B01(RomoteSolution) RCU in Step 2 ?
Press [*] + [#] keys to repair RCU ?
Thanks.

(ALTech) Eric Kim

2019-03-25 19:05

developer   ~0001701

Hi Kerwin,

Yes, tried BT pairing of BRM-B01(RomoteSolution) RCU with [*]+[#] keys.

(SW) Kerwin Chen

2019-03-26 21:42

developer   ~0001714

Hi Eric,

Is [Expected Result] described above correct ?
Since user press [*]+[#] keys on BRM-B01(RomoteSolution) RCU to repair, STB should pair with this RCU.
Please help to confirm, thanks !

(ALTech) Eric Kim

2019-03-27 10:27

developer   ~0001724

Hi Kerwin,

Let me check the refernce STB in order to verify the correct behavior and get back to you by the end of the day.

(ALTech) Eric Kim

2019-03-27 11:25

developer   ~0001726

Hi Kerwin,

Just verified it with the reference STB(Kaon).
The connected BT is not disconnected until another RCU's BT connection is done.
In other words, Kaon STB keeps the original BT connection since another RCU's BT connection is failed.

(ALTech) Eric Kim

2019-03-27 12:08

developer   ~0001728

Last edited: 2019-03-27 12:47

Hi Kerwin,

We've checked the reference STB's behavior more.
To sum up, the reference STB's behavior is as follows.

1) In case of trying to pair BT again with the same RCU
    -. If BT connection is failed due to any cause when trying to repair with the same RCU, the original BT is in only pairing status and BT connection is disconnected

2) In case of trying to pair BT with another RCU
    -. As I already mentioned, the connected BT is not disconnected until another RCU's BT connection is done.
    -. In other workds, STB keeps the original BT connection since another RCU's BT connection is failed.

Please distinguish the scenario between the same RCU and other RCU.

(SW) Kerwin Chen

2019-04-02 14:37

developer   ~0001817

Hi Eric,

We already remove our unpair program onV15.502.9 release.
Since TVS provide the same pairing program, RCU pairing and unpairing behavior should be the same as reference STB.

Please check if the issue still exists or not.
BTW, please make sure to clear RCU pair information and reinstall battery before you start to test.

(ALTech) Eric Kim

2019-04-02 15:18

developer   ~0001821

Hi Kerwin,

Thanks for your active support.

Just verified this issue with RCU's latest version(v1.30) + STB's v15.502.9.
The behavior on BT pairing and connection got better over all, and also BT behavior both for retrying BT connection with the same RCU and for trying BT connection with another RCU got better than previous one.

This issue has not been reproduced yet, and it seems to be impoved.

(SW) Kerwin Chen

2019-04-02 20:04

developer   ~0001836

included in v15.502.9

(ALTech) Eric Kim

2019-04-17 09:11

developer   ~0002044

Just verified it again with v15.502.12. It's fixed.

Issue History

Date Modified Username Field Change
2019-03-25 16:45 (ALTech) Eric Kim New Issue
2019-03-25 16:45 (ALTech) Eric Kim Status new => assigned
2019-03-25 16:45 (ALTech) Eric Kim Assigned To => (SW) Kerwin Chen
2019-03-25 16:45 (ALTech) Eric Kim File Added: LogFilter_20190325_171142.7z
2019-03-25 16:45 (ALTech) Eric Kim Issue Monitored: (ALTech) SY Yoon
2019-03-25 16:45 (ALTech) Eric Kim Issue Monitored: (SW) Jacky Chiang
2019-03-25 16:45 (ALTech) Eric Kim Issue Monitored: (ALTech) Jewoo Lee
2019-03-25 18:05 (SW) Kerwin Chen Note Added: 0001700
2019-03-25 19:05 (ALTech) Eric Kim Note Added: 0001701
2019-03-26 21:42 (SW) Kerwin Chen Note Added: 0001714
2019-03-27 10:27 (ALTech) Eric Kim Note Added: 0001724
2019-03-27 11:25 (ALTech) Eric Kim Note Added: 0001726
2019-03-27 12:08 (ALTech) Eric Kim Note Added: 0001728
2019-03-27 12:47 (ALTech) Eric Kim Note Edited: 0001728
2019-04-02 14:37 (SW) Kerwin Chen Note Added: 0001817
2019-04-02 15:18 (ALTech) Eric Kim Note Added: 0001821
2019-04-02 20:04 (SW) Kerwin Chen Assigned To (SW) Kerwin Chen => (ALTech) Eric Kim
2019-04-02 20:04 (SW) Kerwin Chen Status assigned => resolved
2019-04-02 20:04 (SW) Kerwin Chen Resolution open => fixed
2019-04-02 20:04 (SW) Kerwin Chen Note Added: 0001836
2019-04-17 09:11 (ALTech) Eric Kim Status resolved => closed
2019-04-17 09:11 (ALTech) Eric Kim Note Added: 0002044